@anthony-c-martin Working on the fixing the tests, so did not check the checklist yet. done.

@anthony-c-martin Could you take a look at this PR? 😃 I have updated the code to the new structure. If this isn’t a feature or tool the team is looking for, feel free to close it.

@johnlokerse sorry for the delay. The way this is implemented looks good to me. My hesitancy is that Bicep would be linking to GitHub repos that are outside of Microsoft's control from official product code.

For example, if one of these accounts were to be compromised, we would have no way of detecting or shutting it down. I'm seeking guidance from the PM team on how to proceed.

@johnlokerse sorry for the delay. The way this is implemented looks good to me. My hesitancy is that Bicep would be linking to GitHub repos that are outside of Microsoft's control from official product code.

For example, if one of these accounts were to be compromised, we would have no way of detecting or shutting it down. I'm seeking guidance from the PM team on how to proceed.

@anthony-c-martin Good point. I didn't think about that scenario. Would a small description of each repository suffice? If yes, then this tool is only informative and it would still be great for planning, context gathering and exploring. The next question would be how a user can find the actual content needed to use the extension.

I see a feature request coming for an official Azure Bicep Extension Marketplace 😄